Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ae3f9333cfe7926947d6885068ef01f0d60e74d09187141103409b9ae5b52f6

Tx prefix hash: 02cf89cd0f4fde49aa24e3890ad47040eefccdd237263344a27a1df4c1e4d226
Tx public key: 5e131691768d76f6f998062f5f465416b2ab0a120d3240c489a621383a770bde
Timestamp: 1750827615 Timestamp [UCT]: 2025-06-25 05:00:15 Age [y:d:h:m:s]: 00:141:23:45:43
Block: 1312307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99405 RingCT/type: yes/0
Extra: 015e131691768d76f6f998062f5f465416b2ab0a120d3240c489a621383a770bde02110000000e43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b9f5a72fc5b7f82b18da5967d8bfd8b6c0dca10dde27d1cf6a1eb434082b0ca 0.600000000000 1799940 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": 1312317, "vin": [ { "gen": { "height": 1312307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b9f5a72fc5b7f82b18da5967d8bfd8b6c0dca10dde27d1cf6a1eb434082b0ca" } } ], "extra": [ 1, 94, 19, 22, 145, 118, 141, 118, 246, 249, 152, 6, 47, 95, 70, 84, 22, 178, 171, 10, 18, 13, 50, 64, 196, 137, 166, 33, 56, 58, 119, 11, 222, 2, 17, 0, 0, 0, 14, 67, 132, 109, 102, 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