Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0c7b79f63673b52bef4214d5ca4930edda24e3819ad472e89b35e6658b3824

Tx prefix hash: a5b53d3d7405804d5e2531ef61e32ebfd5c0382a2dd362fecff28f1f86723021
Tx public key: e6afc4f46532abebf59ef181aa2f65f161685e02198acefec2e7c0083fd4fda5
Timestamp: 1728983261 Timestamp [UCT]: 2024-10-15 09:07:41 Age [y:d:h:m:s]: 00:150:15:47:58
Block: 1132039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107456 RingCT/type: yes/0
Extra: 01e6afc4f46532abebf59ef181aa2f65f161685e02198acefec2e7c0083fd4fda5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac67cb471d4bad61e3ff5daf953b0c9d9a05f9aedccc6a3f40255c02dfb050c 0.600000000000 1614948 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": 1132049, "vin": [ { "gen": { "height": 1132039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac67cb471d4bad61e3ff5daf953b0c9d9a05f9aedccc6a3f40255c02dfb050c" } } ], "extra": [ 1, 230, 175, 196, 244, 101, 50, 171, 235, 245, 158, 241, 129, 170, 47, 101, 241, 97, 104, 94, 2, 25, 138, 206, 254, 194, 231, 192, 8, 63, 212, 253, 165, 2, 17, 0, 0, 0, 2, 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