Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339e5caf70a1e8890b66d2741e99cc552c3b85e01623a13626d7adbda678fd4a

Tx prefix hash: 03f2e869e93ac1b6159a693ae32ccfca0242453bbe3cfe464c38b5d91254e413
Tx public key: a2d2cec8f7b398064c95376bed0b9e7063401cfb09a89c04f763c57c8a1e2da5
Timestamp: 1639161977 Timestamp [UCT]: 2021-12-10 18:46:17 Age [y:d:h:m:s]: 03:094:11:58:57
Block: 392684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846265 RingCT/type: yes/0
Extra: 01a2d2cec8f7b398064c95376bed0b9e7063401cfb09a89c04f763c57c8a1e2da50211000000031cab2639000000000000000000

1 output(s) for total of 30.681936116000 dcy

stealth address amount amount idx
00: 0667babe3793c276e946c4d881f1fffd535de10f98ad88bb69fad8c674a0bb2c 30.681936116000 789643 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": 392694, "vin": [ { "gen": { "height": 392684 } } ], "vout": [ { "amount": 30681936116, "target": { "key": "0667babe3793c276e946c4d881f1fffd535de10f98ad88bb69fad8c674a0bb2c" } } ], "extra": [ 1, 162, 210, 206, 200, 247, 179, 152, 6, 76, 149, 55, 107, 237, 11, 158, 112, 99, 64, 28, 251, 9, 168, 156, 4, 247, 99, 197, 124, 138, 30, 45, 165, 2, 17, 0, 0, 0, 3, 28, 171, 38, 57, 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