Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e768caad59ba251207ec0d3165c7ea9fcbbc87df25b464478f4611d0226c7697

Tx prefix hash: abc46234c269f83741bb8df3bde2396e765bbe5c7c3e82e0038e07c4ad0c198c
Tx public key: f9c25427ed72d33928d4dca513ef5fab9599eecfcff1822a42e3aaee8f83a07b
Timestamp: 1717694897 Timestamp [UCT]: 2024-06-06 17:28:17 Age [y:d:h:m:s]: 01:157:16:13:20
Block: 1038449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371263 RingCT/type: yes/0
Extra: 01f9c25427ed72d33928d4dca513ef5fab9599eecfcff1822a42e3aaee8f83a07b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a59de14d48cfa08bd654419fac0c41000594b4b04bfd7fba91b25e712fb2179 0.600000000000 1507010 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": 1038459, "vin": [ { "gen": { "height": 1038449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a59de14d48cfa08bd654419fac0c41000594b4b04bfd7fba91b25e712fb2179" } } ], "extra": [ 1, 249, 194, 84, 39, 237, 114, 211, 57, 40, 212, 220, 165, 19, 239, 95, 171, 149, 153, 238, 207, 207, 241, 130, 42, 66, 227, 170, 238, 143, 131, 160, 123, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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