Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8337a80b8fa1ddfd43492bc3973feb69d401e3051ce50ef08fee390e106fa9d4

Tx prefix hash: b6b70869c949ea582b962f206ef4bf2a24442274d0b5743fca39e8b0e4c370a4
Tx public key: 9936d2c8e91998aeeb01814c4cdd74fd6d0e26ecd938dac8a2ab46850b765c1c
Timestamp: 1685864322 Timestamp [UCT]: 2023-06-04 07:38:42 Age [y:d:h:m:s]: 02:012:03:57:01
Block: 774795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530712 RingCT/type: yes/0
Extra: 019936d2c8e91998aeeb01814c4cdd74fd6d0e26ecd938dac8a2ab46850b765c1c021100000003faf35c9c000000000000000000

1 output(s) for total of 1.662580564000 dcy

stealth address amount amount idx
00: ee46f0f1de963cb46e7c73e14cb70515ea6b5363d7342df164fef2f2ee4b865a 1.662580564000 1224282 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": 774805, "vin": [ { "gen": { "height": 774795 } } ], "vout": [ { "amount": 1662580564, "target": { "key": "ee46f0f1de963cb46e7c73e14cb70515ea6b5363d7342df164fef2f2ee4b865a" } } ], "extra": [ 1, 153, 54, 210, 200, 233, 25, 152, 174, 235, 1, 129, 76, 76, 221, 116, 253, 109, 14, 38, 236, 217, 56, 218, 200, 162, 171, 70, 133, 11, 118, 92, 28, 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