Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e3ab4355f040da90028a470f495f0faf196ace62196c22a0a536f844fea00d

Tx prefix hash: b7f0448ba0e1e7ed052e75b025c8765977c13c41c04cf0d37755f6baea5bc347
Tx public key: e0fa474735aa7487e8d28237d0b9fbdbd3318cf75ca5ecdcd8cf5c80d2b42fbb
Timestamp: 1755189472 Timestamp [UCT]: 2025-08-14 16:37:52 Age [y:d:h:m:s]: 00:097:09:13:21
Block: 1346767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69158 RingCT/type: yes/0
Extra: 01e0fa474735aa7487e8d28237d0b9fbdbd3318cf75ca5ecdcd8cf5c80d2b42fbb0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4d2ac6628dfb1819fd6c2e73dd206383b159be80f4d2c15753d6515198eb0ac 0.600000000000 1834672 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": 1346777, "vin": [ { "gen": { "height": 1346767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4d2ac6628dfb1819fd6c2e73dd206383b159be80f4d2c15753d6515198eb0ac" } } ], "extra": [ 1, 224, 250, 71, 71, 53, 170, 116, 135, 232, 210, 130, 55, 208, 185, 251, 219, 211, 49, 140, 247, 92, 165, 236, 220, 216, 207, 92, 128, 210, 180, 47, 187, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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