Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec706388a30001edb6066f95b9dcf866708e7b0d70a7ab3d4d2800432f1406a1

Tx prefix hash: cd313c52e621a864143f0eae773bdb8f83b8abd47b377ec8de919ae0a10fa778
Tx public key: 56e1331313d70f29a463d840dc5b06a22f62b98f8abec143012e528718fc25b8
Timestamp: 1741144685 Timestamp [UCT]: 2025-03-05 03:18:05 Age [y:d:h:m:s]: 00:333:09:44:45
Block: 1232397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235946 RingCT/type: yes/0
Extra: 0156e1331313d70f29a463d840dc5b06a22f62b98f8abec143012e528718fc25b80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97281fca1601529c6e549d9f06fb9dc26d94f499279a752a58a1532f97f51cfd 0.600000000000 1719310 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": 1232407, "vin": [ { "gen": { "height": 1232397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97281fca1601529c6e549d9f06fb9dc26d94f499279a752a58a1532f97f51cfd" } } ], "extra": [ 1, 86, 225, 51, 19, 19, 215, 15, 41, 164, 99, 216, 64, 220, 91, 6, 162, 47, 98, 185, 143, 138, 190, 193, 67, 1, 46, 82, 135, 24, 252, 37, 184, 2, 17, 0, 0, 0, 4, 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