Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0302b44e3f3f9a634a4b6cbf5a9b7c028637e699b8710ba8813e2e55691d3db

Tx prefix hash: a7f5ee7878fb451bae59c51e739430762dc3e8b7d34ba22f542ee66abbb7925c
Tx public key: ea42380317d22a44a011dde314e6fd08ae3de5e2795fa22a50dabe74c444917d
Timestamp: 1735510026 Timestamp [UCT]: 2024-12-29 22:07:06 Age [y:d:h:m:s]: 00:353:03:55:53
Block: 1186004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249971 RingCT/type: yes/0
Extra: 01ea42380317d22a44a011dde314e6fd08ae3de5e2795fa22a50dabe74c444917d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 120488003581b950d5647df8d9bcc44fa3bbccf87d2821c6a12c4b01878771d9 0.600000000000 1672479 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": 1186014, "vin": [ { "gen": { "height": 1186004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "120488003581b950d5647df8d9bcc44fa3bbccf87d2821c6a12c4b01878771d9" } } ], "extra": [ 1, 234, 66, 56, 3, 23, 210, 42, 68, 160, 17, 221, 227, 20, 230, 253, 8, 174, 61, 229, 226, 121, 95, 162, 42, 80, 218, 190, 116, 196, 68, 145, 125, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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