Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2347d8a94c6ca01d7ad0b33460ed7136febcc31fa49d94c59f522163db5c3195

Tx prefix hash: 312597ec7419f3011520105b78f206ff21fa81c814af667c0c74f0c344a0d546
Tx public key: 7a3c8e24b0e52b3f744a59d126c1143fb7d62490c0097743f2dc66d535ee3c52
Timestamp: 1716800834 Timestamp [UCT]: 2024-05-27 09:07:14 Age [y:d:h:m:s]: 00:357:15:43:56
Block: 1031049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255641 RingCT/type: yes/0
Extra: 017a3c8e24b0e52b3f744a59d126c1143fb7d62490c0097743f2dc66d535ee3c520211000000110011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e11f3de15bd1c947a6506f064806ea7828fd60871c6f513ff8ca5bfa28286e5 0.600000000000 1499396 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": 1031059, "vin": [ { "gen": { "height": 1031049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e11f3de15bd1c947a6506f064806ea7828fd60871c6f513ff8ca5bfa28286e5" } } ], "extra": [ 1, 122, 60, 142, 36, 176, 229, 43, 63, 116, 74, 89, 209, 38, 193, 20, 63, 183, 214, 36, 144, 192, 9, 119, 67, 242, 220, 102, 213, 53, 238, 60, 82, 2, 17, 0, 0, 0, 17, 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