Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef82171ff404d5a532c1e16fd80c84550b41abf9a2fbd12e4959892fe5b4b18

Tx prefix hash: 53775d6966fcb57b8225258aeaba3bbfe1670cba02facd330726061c5a97fbca
Tx public key: b15a0997e9a088161ebfbd3cc386e3b283fe340b9f960d92a15d3840f2cf3315
Timestamp: 1657059043 Timestamp [UCT]: 2022-07-05 22:10:43 Age [y:d:h:m:s]: 02:303:03:50:19
Block: 537455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737812 RingCT/type: yes/0
Extra: 01b15a0997e9a088161ebfbd3cc386e3b283fe340b9f960d92a15d3840f2cf331502110000000a33af99f4000000000000000000

1 output(s) for total of 10.166901768000 dcy

stealth address amount amount idx
00: bc3c14c6e7817b0057973b6567aea1d5b9c6aaa816d04e175e3e24dff146f375 10.166901768000 967344 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": 537465, "vin": [ { "gen": { "height": 537455 } } ], "vout": [ { "amount": 10166901768, "target": { "key": "bc3c14c6e7817b0057973b6567aea1d5b9c6aaa816d04e175e3e24dff146f375" } } ], "extra": [ 1, 177, 90, 9, 151, 233, 160, 136, 22, 30, 191, 189, 60, 195, 134, 227, 178, 131, 254, 52, 11, 159, 150, 13, 146, 161, 93, 56, 64, 242, 207, 51, 21, 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