Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c3c6f53df268c014ba0fc55c24b39ce6294357a151b8182ae5f3bb56f97a589

Tx prefix hash: 016a621a4fca6f0186229de5d277cd9686ada1b2e9fa5121aaf6604951542bb2
Tx public key: 37323f80af69315d4b13113627866fe4b049ef55efb621aa91d53ea7d29c92b8
Timestamp: 1717530581 Timestamp [UCT]: 2024-06-04 19:49:41 Age [y:d:h:m:s]: 01:016:14:31:56
Block: 1037088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272599 RingCT/type: yes/0
Extra: 0137323f80af69315d4b13113627866fe4b049ef55efb621aa91d53ea7d29c92b80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c8c571c5454fe76d0ae066ba6cbdcad375e16f7f9c8415c6e6ba1abb2143131 0.600000000000 1505619 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": 1037098, "vin": [ { "gen": { "height": 1037088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c8c571c5454fe76d0ae066ba6cbdcad375e16f7f9c8415c6e6ba1abb2143131" } } ], "extra": [ 1, 55, 50, 63, 128, 175, 105, 49, 93, 75, 19, 17, 54, 39, 134, 111, 228, 176, 73, 239, 85, 239, 182, 33, 170, 145, 213, 62, 167, 210, 156, 146, 184, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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