Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87569afc014b7e0845087d635f225237e55c5bca936515180ae66d5273f4090

Tx prefix hash: 243d217f7dfd2e01c789eed4231d0abfd8d46bb4047ca62db816dc35cc2b5f8f
Tx public key: 307780f7f4b64d3d6f7ce5b103df839114b72acdbe70fed5c3b4e4dcd852bd45
Timestamp: 1581515310 Timestamp [UCT]: 2020-02-12 13:48:30 Age [y:d:h:m:s]: 04:281:22:40:05
Block: 63463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093647 RingCT/type: yes/0
Extra: 01307780f7f4b64d3d6f7ce5b103df839114b72acdbe70fed5c3b4e4dcd852bd45021100000002c71d3ff9000000000000000000

1 output(s) for total of 378.200021774000 dcy

stealth address amount amount idx
00: 2b528d27cb272fb935196381132be980fed91b1e0a6b6f64a327a4c3e7a85623 378.200021774000 117019 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": 63473, "vin": [ { "gen": { "height": 63463 } } ], "vout": [ { "amount": 378200021774, "target": { "key": "2b528d27cb272fb935196381132be980fed91b1e0a6b6f64a327a4c3e7a85623" } } ], "extra": [ 1, 48, 119, 128, 247, 244, 182, 77, 61, 111, 124, 229, 177, 3, 223, 131, 145, 20, 183, 42, 205, 190, 112, 254, 213, 195, 180, 228, 220, 216, 82, 189, 69, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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