Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41846c44eb1508385d84244cd03999ff44642597a1b38aeeb9c380e94815199d

Tx prefix hash: 462f3ba7afcd5d8fcb6076e1bbbc89a8a7980b299bfe0b24cfc3efaad8fd5b5e
Tx public key: f9efb576d36ae1800c09a6832ae2aa3048a2188c43fd57590a75ea65c8861867
Timestamp: 1694965506 Timestamp [UCT]: 2023-09-17 15:45:06 Age [y:d:h:m:s]: 01:128:10:44:51
Block: 850202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353064 RingCT/type: yes/0
Extra: 01f9efb576d36ae1800c09a6832ae2aa3048a2188c43fd57590a75ea65c88618670211000000234b8f5122000000000000000000

1 output(s) for total of 0.935250383000 dcy

stealth address amount amount idx
00: f9a44e077e0229bf7402ae024d32d8d180673f4714cafe90a9225d49a07e0dc2 0.935250383000 1303910 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": 850212, "vin": [ { "gen": { "height": 850202 } } ], "vout": [ { "amount": 935250383, "target": { "key": "f9a44e077e0229bf7402ae024d32d8d180673f4714cafe90a9225d49a07e0dc2" } } ], "extra": [ 1, 249, 239, 181, 118, 211, 106, 225, 128, 12, 9, 166, 131, 42, 226, 170, 48, 72, 162, 24, 140, 67, 253, 87, 89, 10, 117, 234, 101, 200, 134, 24, 103, 2, 17, 0, 0, 0, 35, 75, 143, 81, 34, 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