Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef22c2511f0f88d4a487a6d43dfdaafceb433bace7ee73139ec5fe86cba93871

Tx prefix hash: 825796796ecfd0abffbd2ae6acc54c6ba14f48eec36d93072836e38eae0f36e4
Tx public key: 624195eb80415ae19259cc32aa715b7ace796d4bbca0c35ba4b4fd5b268a97ef
Timestamp: 1757129620 Timestamp [UCT]: 2025-09-06 03:33:40 Age [y:d:h:m:s]: 00:090:00:52:44
Block: 1362354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64397 RingCT/type: yes/0
Extra: 01624195eb80415ae19259cc32aa715b7ace796d4bbca0c35ba4b4fd5b268a97ef02110000000bb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 676bed397ad569eb5bccbc5990a797973b79724c3d3a59c40e52d1ae7292963e 0.600000000000 1850385 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": 1362364, "vin": [ { "gen": { "height": 1362354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "676bed397ad569eb5bccbc5990a797973b79724c3d3a59c40e52d1ae7292963e" } } ], "extra": [ 1, 98, 65, 149, 235, 128, 65, 90, 225, 146, 89, 204, 50, 170, 113, 91, 122, 206, 121, 109, 75, 188, 160, 195, 91, 164, 180, 253, 91, 38, 138, 151, 239, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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