Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d41781b57be90ade1f27eb5b8c488be16414186193309546e23a28bc3755aec2

Tx prefix hash: 6059d9b3efd18bbca9bbe06d0b87fc0d8c8b33bc65163877b970f37fa8dcd46d
Tx public key: 735b27c12152c03ab90b5e4716a02ad8e9f3a09e4e2a49ac6970a781767c9a3b
Timestamp: 1720813271 Timestamp [UCT]: 2024-07-12 19:41:11 Age [y:d:h:m:s]: 00:300:04:19:17
Block: 1064306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214477 RingCT/type: yes/0
Extra: 01735b27c12152c03ab90b5e4716a02ad8e9f3a09e4e2a49ac6970a781767c9a3b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d53a1b6fea8f4cd7bc28bb4cd2ac2339d72503c63a14f4b2b10b910798cdbe3 0.600000000000 1534831 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": 1064316, "vin": [ { "gen": { "height": 1064306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d53a1b6fea8f4cd7bc28bb4cd2ac2339d72503c63a14f4b2b10b910798cdbe3" } } ], "extra": [ 1, 115, 91, 39, 193, 33, 82, 192, 58, 185, 11, 94, 71, 22, 160, 42, 216, 233, 243, 160, 158, 78, 42, 73, 172, 105, 112, 167, 129, 118, 124, 154, 59, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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