Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bb3d41ab79567b6f1953961b623a71d4e5520695056c92e62a82fa7052b6b36

Tx prefix hash: cacf3f2f63589ab2812c76aec14409949dd303bf8f4700a6383deddb17ac2e8c
Tx public key: 0e350e5ab0a7d2e19b8fef4cb7652141310c84e63673ce1e17c55863a3c0e238
Timestamp: 1704724075 Timestamp [UCT]: 2024-01-08 14:27:55 Age [y:d:h:m:s]: 01:163:12:48:58
Block: 930899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377892 RingCT/type: yes/0
Extra: 010e350e5ab0a7d2e19b8fef4cb7652141310c84e63673ce1e17c55863a3c0e23802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf5ecbcffc3afa4a18523ddd0bbb9679cf1374ecd6f3a2dcf0df49bb84a1e92 0.600000000000 1388789 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": 930909, "vin": [ { "gen": { "height": 930899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf5ecbcffc3afa4a18523ddd0bbb9679cf1374ecd6f3a2dcf0df49bb84a1e92" } } ], "extra": [ 1, 14, 53, 14, 90, 176, 167, 210, 225, 155, 143, 239, 76, 183, 101, 33, 65, 49, 12, 132, 230, 54, 115, 206, 30, 23, 197, 88, 99, 163, 192, 226, 56, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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