Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4904c4e814443cc53d21a26773e4a66d78046d43e502cee11893cc5ec01d2f

Tx prefix hash: 6c4b3383f14689ff74c781258c7d4fc4e94194b1400f820efbe117895259dc7f
Tx public key: 0572d70789db47036fa3bfd124ffffaf0b5d8e253d02998aaffa9363dd24d69e
Timestamp: 1697965788 Timestamp [UCT]: 2023-10-22 09:09:48 Age [y:d:h:m:s]: 01:124:23:07:20
Block: 875086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350279 RingCT/type: yes/0
Extra: 010572d70789db47036fa3bfd124ffffaf0b5d8e253d02998aaffa9363dd24d69e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.773529421000 dcy

stealth address amount amount idx
00: c36d5dce88f99b35450c93d47e3f8e6d7d95460c9eb4d049ad76543fcf785d79 0.773529421000 1330330 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": 875096, "vin": [ { "gen": { "height": 875086 } } ], "vout": [ { "amount": 773529421, "target": { "key": "c36d5dce88f99b35450c93d47e3f8e6d7d95460c9eb4d049ad76543fcf785d79" } } ], "extra": [ 1, 5, 114, 215, 7, 137, 219, 71, 3, 111, 163, 191, 209, 36, 255, 255, 175, 11, 93, 142, 37, 61, 2, 153, 138, 175, 250, 147, 99, 221, 36, 214, 158, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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