Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 346b818ee11e228d8753a917cc0de682c31f4fd6cc11b85dca813e0ee7714984

Tx prefix hash: 2aada1cc9585eca4f05eddda0c1d41a3ade865dcb680db05c8badd2015956f1c
Tx public key: 87a27b5fd4e11ce8a1960508d4bf93c54a13f4c5e2b242aebafab63b6d7a6d98
Timestamp: 1704025640 Timestamp [UCT]: 2023-12-31 12:27:20 Age [y:d:h:m:s]: 01:165:21:55:39
Block: 925111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379669 RingCT/type: yes/0
Extra: 0187a27b5fd4e11ce8a1960508d4bf93c54a13f4c5e2b242aebafab63b6d7a6d980211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d37d580351e625fbcec468a165bbca4fb755a93c5fa91e665a73000532e1519 0.600000000000 1382871 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": 925121, "vin": [ { "gen": { "height": 925111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d37d580351e625fbcec468a165bbca4fb755a93c5fa91e665a73000532e1519" } } ], "extra": [ 1, 135, 162, 123, 95, 212, 225, 28, 232, 161, 150, 5, 8, 212, 191, 147, 197, 74, 19, 244, 197, 226, 178, 66, 174, 186, 250, 182, 59, 109, 122, 109, 152, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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