Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7106e8123602ea96845befb66103427011739308512ba9e0d73be7b9c8519b9e

Tx prefix hash: 988fb95be6c91e8b9285662433c98e6ee1e60e13194edfc2bd1e57ff67f67a7e
Tx public key: 5cfdbff504e3efce8310cc601f2ebe697741d8230903f5b6c39f20fcd69b49ff
Timestamp: 1698439371 Timestamp [UCT]: 2023-10-27 20:42:51 Age [y:d:h:m:s]: 01:221:06:59:34
Block: 879016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419208 RingCT/type: yes/0
Extra: 015cfdbff504e3efce8310cc601f2ebe697741d8230903f5b6c39f20fcd69b49ff02110000000a33af99f4000000000000000000

1 output(s) for total of 0.750680456000 dcy

stealth address amount amount idx
00: 8ebe779fd8cbc7de547cf3aba4e4ae270251e0c83f461509947bb2f6f4cbfe63 0.750680456000 1334514 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": 879026, "vin": [ { "gen": { "height": 879016 } } ], "vout": [ { "amount": 750680456, "target": { "key": "8ebe779fd8cbc7de547cf3aba4e4ae270251e0c83f461509947bb2f6f4cbfe63" } } ], "extra": [ 1, 92, 253, 191, 245, 4, 227, 239, 206, 131, 16, 204, 96, 31, 46, 190, 105, 119, 65, 216, 35, 9, 3, 245, 182, 195, 159, 32, 252, 214, 155, 73, 255, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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