Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6d84945cf132984c25913e798c119ce8216a8e276ee001f89e06bf455e6cec4

Tx prefix hash: 0efbca78126fb6dd76439371b7133bf11b83d042b820bd8b872761559c690ce5
Tx public key: 421e692d710cacc3fbde1cbcfe3aade10f0c13deead57088832e5ff438cf2c79
Timestamp: 1648131204 Timestamp [UCT]: 2022-03-24 14:13:24 Age [y:d:h:m:s]: 02:356:01:03:48
Block: 465438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 773767 RingCT/type: yes/0
Extra: 01421e692d710cacc3fbde1cbcfe3aade10f0c13deead57088832e5ff438cf2c790211000000034a0f5013000000000000000000

1 output(s) for total of 17.612092172000 dcy

stealth address amount amount idx
00: 0e3f1cc27f944774fd6140fd315d8cd22edd4f0d8af89afaff4eb2b6cd8e6cf7 17.612092172000 883541 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": 465448, "vin": [ { "gen": { "height": 465438 } } ], "vout": [ { "amount": 17612092172, "target": { "key": "0e3f1cc27f944774fd6140fd315d8cd22edd4f0d8af89afaff4eb2b6cd8e6cf7" } } ], "extra": [ 1, 66, 30, 105, 45, 113, 12, 172, 195, 251, 222, 28, 188, 254, 58, 173, 225, 15, 12, 19, 222, 234, 213, 112, 136, 131, 46, 95, 244, 56, 207, 44, 121, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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