Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e02192f049b7a757d5311fc5347cc9fb0db430fe322848fc2b92f7cd02381139

Tx prefix hash: 6caf5967824d919ca4e04c1eac73c084413330bfd4401c0fa99bce21f904f129
Tx public key: a135f0781af57e526d3876cfb1c8ef931ed8ab15acc818e7d61af0e5d2e872e3
Timestamp: 1736626894 Timestamp [UCT]: 2025-01-11 20:21:34 Age [y:d:h:m:s]: 00:357:15:22:46
Block: 1195252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253206 RingCT/type: yes/0
Extra: 01a135f0781af57e526d3876cfb1c8ef931ed8ab15acc818e7d61af0e5d2e872e30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d2433d28456c124b5a2ea9ff08f77bc5bc76fbcaf676e8d195acc183188845e 0.600000000000 1681841 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": 1195262, "vin": [ { "gen": { "height": 1195252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d2433d28456c124b5a2ea9ff08f77bc5bc76fbcaf676e8d195acc183188845e" } } ], "extra": [ 1, 161, 53, 240, 120, 26, 245, 126, 82, 109, 56, 118, 207, 177, 200, 239, 147, 30, 216, 171, 21, 172, 200, 24, 231, 214, 26, 240, 229, 210, 232, 114, 227, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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