Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54df3f2d07600829bdaf1e84ddcb3e270e500d80e24dad998720cbfb62e79142

Tx prefix hash: cc23b597eafc5e1d16989763655e00ad437999175487d8a9396045a16da086f1
Tx public key: 82e45b226a8b80c136267ec930aa1fd2bad4a58fd7b81cff688209213fa6d63e
Timestamp: 1750515949 Timestamp [UCT]: 2025-06-21 14:25:49 Age [y:d:h:m:s]: 00:145:04:53:10
Block: 1309809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101617 RingCT/type: yes/0
Extra: 0182e45b226a8b80c136267ec930aa1fd2bad4a58fd7b81cff688209213fa6d63e02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeba7bff20ea4c05319f16ca761b801ea5584502fcd916f56173b3e9a5b6b216 0.600000000000 1797426 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": 1309819, "vin": [ { "gen": { "height": 1309809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeba7bff20ea4c05319f16ca761b801ea5584502fcd916f56173b3e9a5b6b216" } } ], "extra": [ 1, 130, 228, 91, 34, 106, 139, 128, 193, 54, 38, 126, 201, 48, 170, 31, 210, 186, 212, 165, 143, 215, 184, 28, 255, 104, 130, 9, 33, 63, 166, 214, 62, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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