Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d7dd47b755f4950a7e55411cfef74b243ddce4aef8367728897f1f2cdcb7f43

Tx prefix hash: 7527c8e5437f76af095f418aae5777c37fb6b88e30475573570c71a1eb23a7e8
Tx public key: 132b2fe78dfaeb11b130871659aa92342c0a4ce6f3dd78e7eff7f5f079baeef0
Timestamp: 1700155394 Timestamp [UCT]: 2023-11-16 17:23:14 Age [y:d:h:m:s]: 01:213:23:27:36
Block: 893033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414040 RingCT/type: yes/0
Extra: 01132b2fe78dfaeb11b130871659aa92342c0a4ce6f3dd78e7eff7f5f079baeef002110000000675e3f0e9000000000000000000

1 output(s) for total of 0.674545033000 dcy

stealth address amount amount idx
00: 48dcee56cac5827ba463ad926a09471f8f65f7392d27a89631fc27da3bfbec1a 0.674545033000 1349196 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": 893043, "vin": [ { "gen": { "height": 893033 } } ], "vout": [ { "amount": 674545033, "target": { "key": "48dcee56cac5827ba463ad926a09471f8f65f7392d27a89631fc27da3bfbec1a" } } ], "extra": [ 1, 19, 43, 47, 231, 141, 250, 235, 17, 177, 48, 135, 22, 89, 170, 146, 52, 44, 10, 76, 230, 243, 221, 120, 231, 239, 247, 245, 240, 121, 186, 238, 240, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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