Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bf9678fa6b22fd453d2e023b2bc212aa2ce0173943257559698acb81b2c5f3e

Tx prefix hash: a366be418a96617dad21ab8f2bd39c53799b12c847b69837f438b71c8ac64ef2
Tx public key: bbd8d238a9e287d2be428d80cdcb2ec61e49215f46122a15d24e9c566323972b
Timestamp: 1710128356 Timestamp [UCT]: 2024-03-11 03:39:16 Age [y:d:h:m:s]: 01:023:14:01:43
Block: 975721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277838 RingCT/type: yes/0
Extra: 01bbd8d238a9e287d2be428d80cdcb2ec61e49215f46122a15d24e9c566323972b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 695be6b5603c34a609dcec0dc1382a68f5bcaab759fd45f3d39f512a9cf8cfcd 0.600000000000 1435694 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": 975731, "vin": [ { "gen": { "height": 975721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "695be6b5603c34a609dcec0dc1382a68f5bcaab759fd45f3d39f512a9cf8cfcd" } } ], "extra": [ 1, 187, 216, 210, 56, 169, 226, 135, 210, 190, 66, 141, 128, 205, 203, 46, 198, 30, 73, 33, 95, 70, 18, 42, 21, 210, 78, 156, 86, 99, 35, 151, 43, 2, 17, 0, 0, 0, 1, 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