Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84aef92134d05abf0a123d7bc7be4d49cdba063638e487dc2547700f2f1c14a7

Tx prefix hash: 5c3b61e102dbe80ed25995dbe9354045d45cda681536ac603d7e5cfdcf926e4f
Tx public key: 346050f8e2ff5aeb43fbc177f7524336b68cbe0454d1a143dfe8cd9de3994c17
Timestamp: 1676591811 Timestamp [UCT]: 2023-02-16 23:56:51 Age [y:d:h:m:s]: 01:310:22:56:26
Block: 698567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483196 RingCT/type: yes/0
Extra: 01346050f8e2ff5aeb43fbc177f7524336b68cbe0454d1a143dfe8cd9de3994c17021100000007835e4d22000000000000000000

1 output(s) for total of 2.974112932000 dcy

stealth address amount amount idx
00: 61e5f482ec38502c67da567daa546f8a8dec07bda1afb9f6597047b8c31d654e 2.974112932000 1141876 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": 698577, "vin": [ { "gen": { "height": 698567 } } ], "vout": [ { "amount": 2974112932, "target": { "key": "61e5f482ec38502c67da567daa546f8a8dec07bda1afb9f6597047b8c31d654e" } } ], "extra": [ 1, 52, 96, 80, 248, 226, 255, 90, 235, 67, 251, 193, 119, 247, 82, 67, 54, 182, 140, 190, 4, 84, 209, 161, 67, 223, 232, 205, 157, 227, 153, 76, 23, 2, 17, 0, 0, 0, 7, 131, 94, 77, 34, 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