Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf97272e270389e83efa9e1e8abcfc98445520454cc1f70871afe5f52d09a3c

Tx prefix hash: be0e86d7b76dd7953f193ba2f1a8429632d8aa92e4a6505c3f7fd853bd2dd589
Tx public key: 7b2df695e4e203c55085c1229131b3fff672613449e9e32156fa19bceed11001
Timestamp: 1718332752 Timestamp [UCT]: 2024-06-14 02:39:12 Age [y:d:h:m:s]: 00:224:20:56:45
Block: 1043748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160861 RingCT/type: yes/0
Extra: 017b2df695e4e203c55085c1229131b3fff672613449e9e32156fa19bceed110010211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f275056d524d74efaf1d151f9e9e62034f5ef215252c512bc3c9380c017f8829 0.600000000000 1512907 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": 1043758, "vin": [ { "gen": { "height": 1043748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f275056d524d74efaf1d151f9e9e62034f5ef215252c512bc3c9380c017f8829" } } ], "extra": [ 1, 123, 45, 246, 149, 228, 226, 3, 197, 80, 133, 193, 34, 145, 49, 179, 255, 246, 114, 97, 52, 73, 233, 227, 33, 86, 250, 25, 188, 238, 209, 16, 1, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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