Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a6484959a5ee61f09a17176902f0f5d1ee32ba27015d7fa02938cbc8e43d12

Tx prefix hash: 8431629dbbc565fa29c54d48b40b80edfe79f7f30e45d7a8353819654f192469
Tx public key: 0ee9634cb03e6e9eea5e9669def5587ef568a38a6b54d66071922b4abbde1fdb
Timestamp: 1762437408 Timestamp [UCT]: 2025-11-06 13:56:48 Age [y:d:h:m:s]: 00:007:18:55:38
Block: 1406238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5602 RingCT/type: yes/0
Extra: 010ee9634cb03e6e9eea5e9669def5587ef568a38a6b54d66071922b4abbde1fdb02110000000bdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99f294a9fa2d8d19025a4f7ec93af4cf4a02c75a9818e79f942c6b2e40c5df63 0.600000000000 1894621 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": 1406248, "vin": [ { "gen": { "height": 1406238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99f294a9fa2d8d19025a4f7ec93af4cf4a02c75a9818e79f942c6b2e40c5df63" } } ], "extra": [ 1, 14, 233, 99, 76, 176, 62, 110, 158, 234, 94, 150, 105, 222, 245, 88, 126, 245, 104, 163, 138, 107, 84, 214, 96, 113, 146, 43, 74, 187, 222, 31, 219, 2, 17, 0, 0, 0, 11, 223, 90, 36, 122, 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