Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d409972c9ae25e8f2cc84a7d2836c17f18473045ed6188946c1b97951801004

Tx prefix hash: eb14231b0572dcc4895a6efd51fa1136c70eab14cdb194fbcf2617e82b66d07f
Tx public key: 997c466fb210328225ad3097b4ee5d16fb45518b03cbeb886529de840d8a8bdb
Timestamp: 1677357051 Timestamp [UCT]: 2023-02-25 20:30:51 Age [y:d:h:m:s]: 01:281:23:04:08
Block: 704907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462434 RingCT/type: yes/0
Extra: 01997c466fb210328225ad3097b4ee5d16fb45518b03cbeb886529de840d8a8bdb02110000000383600029000000000000000000

1 output(s) for total of 2.833677320000 dcy

stealth address amount amount idx
00: de6c5a1aff47c6f0b9a69ca6ea83fa59c3cf76de0b000b9227f9dbeb9ae3201b 2.833677320000 1148588 of 0

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": 704917, "vin": [ { "gen": { "height": 704907 } } ], "vout": [ { "amount": 2833677320, "target": { "key": "de6c5a1aff47c6f0b9a69ca6ea83fa59c3cf76de0b000b9227f9dbeb9ae3201b" } } ], "extra": [ 1, 153, 124, 70, 111, 178, 16, 50, 130, 37, 173, 48, 151, 180, 238, 93, 22, 251, 69, 81, 139, 3, 203, 235, 136, 101, 41, 222, 132, 13, 138, 139, 219, 2, 17, 0, 0, 0, 3, 131, 96, 0, 41, 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