Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eafbf3a8aa7cfac211b451141a42daa18c4519736dd3961d800d9a806c7da3ef

Tx prefix hash: 19c3bd1ea5246186de4700ce909d83de9f60d664dbf3fa03c5812ef0f579702e
Tx public key: b688128e8e0f29d89c16da6e63f35306b7be080ed2b3d654cb3dc8208b83abb2
Timestamp: 1702925446 Timestamp [UCT]: 2023-12-18 18:50:46 Age [y:d:h:m:s]: 01:148:03:21:13
Block: 916000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367037 RingCT/type: yes/0
Extra: 01b688128e8e0f29d89c16da6e63f35306b7be080ed2b3d654cb3dc8208b83abb202110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ba2a198aa137b9b10443848377e304d3b53ea521325383f07fef7709f5e74b9 0.600000000000 1373434 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": 916010, "vin": [ { "gen": { "height": 916000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba2a198aa137b9b10443848377e304d3b53ea521325383f07fef7709f5e74b9" } } ], "extra": [ 1, 182, 136, 18, 142, 142, 15, 41, 216, 156, 22, 218, 110, 99, 243, 83, 6, 183, 190, 8, 14, 210, 179, 214, 84, 203, 61, 200, 32, 139, 131, 171, 178, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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