Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 716dd84176558f0a35b6cf3526ac2ab90f895c6b485b372c3c2f0c22c73407f3

Tx prefix hash: 243c625998f84c890766c98b47fba47c5d2242f8db64dcbdf5f3aaa81e57c7bb
Tx public key: d356834fd2d5cd789eb3b424044fc6f89a3f4de9e17a884dc412d6bf2baa131d
Timestamp: 1728207185 Timestamp [UCT]: 2024-10-06 09:33:05 Age [y:d:h:m:s]: 01:035:15:41:48
Block: 1125608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283848 RingCT/type: yes/0
Extra: 01d356834fd2d5cd789eb3b424044fc6f89a3f4de9e17a884dc412d6bf2baa131d02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a9e5ef157b4be83aef14251001db3d74f42f80cc0fe3009c496775c30dc965a 0.600000000000 1608359 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1125618, "vin": [ { "gen": { "height": 1125608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a9e5ef157b4be83aef14251001db3d74f42f80cc0fe3009c496775c30dc965a" } } ], "extra": [ 1, 211, 86, 131, 79, 210, 213, 205, 120, 158, 179, 180, 36, 4, 79, 198, 248, 154, 63, 77, 233, 225, 122, 136, 77, 196, 18, 214, 191, 43, 170, 19, 29, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8