Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de93c4939fd18d05e8b4f32dd7998a39c43b563849f3d021e1c9319f3444ab75

Tx prefix hash: ec5feb906fe7c8f15fdc8c2642364f473ebcdcddda402b9299337285a0fbdd7d
Tx public key: 1cac8fb279b1dfd3368aa9beeec1ee1405aa3222577f94676e42691346b2ebb2
Timestamp: 1711751803 Timestamp [UCT]: 2024-03-29 22:36:43 Age [y:d:h:m:s]: 00:335:12:24:00
Block: 989193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239840 RingCT/type: yes/0
Extra: 011cac8fb279b1dfd3368aa9beeec1ee1405aa3222577f94676e42691346b2ebb20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26d08057ad6a17d13c18a86d9fa387cdf45ff1ccb96facd8a74685c2bd79cd9f 0.600000000000 1449488 of 15

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": 989203, "vin": [ { "gen": { "height": 989193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26d08057ad6a17d13c18a86d9fa387cdf45ff1ccb96facd8a74685c2bd79cd9f" } } ], "extra": [ 1, 28, 172, 143, 178, 121, 177, 223, 211, 54, 138, 169, 190, 238, 193, 238, 20, 5, 170, 50, 34, 87, 127, 148, 103, 110, 66, 105, 19, 70, 178, 235, 178, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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