Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16d6b82d56caaa22f852876826d67b7dd592d004b96f322cd2c941fac47cf2e

Tx prefix hash: e3a6e73aa61842f8c5f121a075cd39a3565f0578f6663172f5ebb0cd39a27a96
Tx public key: f8acb43d6daf2f1fcc8cb7e11a56217455b862700ac3364895b80143b0bd5904
Timestamp: 1705477742 Timestamp [UCT]: 2024-01-17 07:49:02 Age [y:d:h:m:s]: 01:079:08:24:49
Block: 937139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317812 RingCT/type: yes/0
Extra: 01f8acb43d6daf2f1fcc8cb7e11a56217455b862700ac3364895b80143b0bd59040211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c6d41ecc2ef29b192976e800a99508dc4314c15b4b81e984a154ae961bcbea9 0.600000000000 1395183 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": 937149, "vin": [ { "gen": { "height": 937139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c6d41ecc2ef29b192976e800a99508dc4314c15b4b81e984a154ae961bcbea9" } } ], "extra": [ 1, 248, 172, 180, 61, 109, 175, 47, 31, 204, 140, 183, 225, 26, 86, 33, 116, 85, 184, 98, 112, 10, 195, 54, 72, 149, 184, 1, 67, 176, 189, 89, 4, 2, 17, 0, 0, 0, 5, 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