Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086ec414792eaa63a48af2d3784d1217fef88bdd62716db6af2531b8f4449ad1

Tx prefix hash: ba7eaa1d6f166212721e7dfe465fbd9fcd5cccaf5bf4a981a26e82d56f1cd8f6
Tx public key: e4aa6ec206a826b40b993657c02c86ade7a49cbee0ad7fa49f38cfb1bbaf7c22
Timestamp: 1582978553 Timestamp [UCT]: 2020-02-29 12:15:53 Age [y:d:h:m:s]: 05:249:22:30:07
Block: 74080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1330657 RingCT/type: yes/0
Extra: 01e4aa6ec206a826b40b993657c02c86ade7a49cbee0ad7fa49f38cfb1bbaf7c2202110000004a7adf42d3000000000000000000

1 output(s) for total of 348.786670116000 dcy

stealth address amount amount idx
00: c3aa7280c04a0eabd2b15ee78ed7adbe151e67634c3a27cd37f9f7922164199e 348.786670116000 136907 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": 74090, "vin": [ { "gen": { "height": 74080 } } ], "vout": [ { "amount": 348786670116, "target": { "key": "c3aa7280c04a0eabd2b15ee78ed7adbe151e67634c3a27cd37f9f7922164199e" } } ], "extra": [ 1, 228, 170, 110, 194, 6, 168, 38, 180, 11, 153, 54, 87, 192, 44, 134, 173, 231, 164, 156, 190, 224, 173, 127, 164, 159, 56, 207, 177, 187, 175, 124, 34, 2, 17, 0, 0, 0, 74, 122, 223, 66, 211, 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