Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b73dc677c705cc53992c47cc5dee129a8361acd51eb6647bcce7b496486e13e

Tx prefix hash: d71c8508ed26ba170ae6da292a8dbb9ab7174785e431f78b2d297299e65b66eb
Tx public key: 30e32bc2f8328b135a16ead1b293e3ac014a719a6555fbe52e571c922a2c6f52
Timestamp: 1723964722 Timestamp [UCT]: 2024-08-18 07:05:22 Age [y:d:h:m:s]: 00:228:07:18:46
Block: 1090433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163028 RingCT/type: yes/0
Extra: 0130e32bc2f8328b135a16ead1b293e3ac014a719a6555fbe52e571c922a2c6f5202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62044d7c87c3ad9371a5494733bd31d5d930ef81b5fb13d6af266113cb0d3410 0.600000000000 1565056 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": 1090443, "vin": [ { "gen": { "height": 1090433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62044d7c87c3ad9371a5494733bd31d5d930ef81b5fb13d6af266113cb0d3410" } } ], "extra": [ 1, 48, 227, 43, 194, 248, 50, 139, 19, 90, 22, 234, 209, 178, 147, 227, 172, 1, 74, 113, 154, 101, 85, 251, 229, 46, 87, 28, 146, 42, 44, 111, 82, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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