Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1b099999a55777dba35e5c6e2c761cb45443ed0d37b87554e1dc6d6eed86b86

Tx prefix hash: df166762853715f8a63655a90fec9f9b5c41119c5847f233c923eff35496f4b5
Tx public key: 76c8a0f8af2296fb7039453a83764f002e67e1a25d043c63c046c76b0b0001ab
Timestamp: 1725887540 Timestamp [UCT]: 2024-09-09 13:12:20 Age [y:d:h:m:s]: 00:201:19:47:32
Block: 1106377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144063 RingCT/type: yes/0
Extra: 0176c8a0f8af2296fb7039453a83764f002e67e1a25d043c63c046c76b0b0001ab02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9f0522f8ed3ca3aebda50d08bd5d818141859346048c17f3a7379ede7b0f286 0.600000000000 1583976 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": 1106387, "vin": [ { "gen": { "height": 1106377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9f0522f8ed3ca3aebda50d08bd5d818141859346048c17f3a7379ede7b0f286" } } ], "extra": [ 1, 118, 200, 160, 248, 175, 34, 150, 251, 112, 57, 69, 58, 131, 118, 79, 0, 46, 103, 225, 162, 93, 4, 60, 99, 192, 70, 199, 107, 11, 0, 1, 171, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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