Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 702bdf32de31b7347bd8a410c16df8350e0ef914dcba7a9c2c7535f59993b7c4

Tx prefix hash: 62def588f6ff1a18f0b95d71f097176839de6ebdccd16757016bb3bc4af88d50
Tx public key: f8119ca48377484bb4d7efa30732594ec4016f453b1c5d58c834c9dc2ea93cdd
Timestamp: 1701675667 Timestamp [UCT]: 2023-12-04 07:41:07 Age [y:d:h:m:s]: 01:177:20:04:44
Block: 905628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388301 RingCT/type: yes/0
Extra: 01f8119ca48377484bb4d7efa30732594ec4016f453b1c5d58c834c9dc2ea93cdd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.612743153000 dcy

stealth address amount amount idx
00: a4d1f04f10828344aeb2cab78a54723cdcfb1c2615899105020a235ee7c20fbc 0.612743153000 1362521 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": 905638, "vin": [ { "gen": { "height": 905628 } } ], "vout": [ { "amount": 612743153, "target": { "key": "a4d1f04f10828344aeb2cab78a54723cdcfb1c2615899105020a235ee7c20fbc" } } ], "extra": [ 1, 248, 17, 156, 164, 131, 119, 72, 75, 180, 215, 239, 163, 7, 50, 89, 78, 196, 1, 111, 69, 59, 28, 93, 88, 200, 52, 201, 220, 46, 169, 60, 221, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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