Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1baa48b080d2931bd0ec53811d1cbe3fc72db7e2de9a39fa87299fc574102769

Tx prefix hash: 414e73eb4f07fd07571a5c50e5ab05aac8e620a14be90d8d325b01e1721b208a
Tx public key: f72a32bc37b41105d96da7c8f75fc1a76d051c2dec5e53d2f3f18542027ad984
Timestamp: 1684626653 Timestamp [UCT]: 2023-05-20 23:50:53 Age [y:d:h:m:s]: 02:173:01:39:14
Block: 764543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643486 RingCT/type: yes/0
Extra: 01f72a32bc37b41105d96da7c8f75fc1a76d051c2dec5e53d2f3f18542027ad984021100000003faf35c9c000000000000000000

1 output(s) for total of 1.797843341000 dcy

stealth address amount amount idx
00: 680b4dca6081762e0000402871652812724ab3e509be89ff70adc4d9c9d2ee07 1.797843341000 1213486 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": 764553, "vin": [ { "gen": { "height": 764543 } } ], "vout": [ { "amount": 1797843341, "target": { "key": "680b4dca6081762e0000402871652812724ab3e509be89ff70adc4d9c9d2ee07" } } ], "extra": [ 1, 247, 42, 50, 188, 55, 180, 17, 5, 217, 109, 167, 200, 247, 95, 193, 167, 109, 5, 28, 45, 236, 94, 83, 210, 243, 241, 133, 66, 2, 122, 217, 132, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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