Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee17925059f9b0a80bba7f08225d64616050eebc5431f151c78ab21c94fbf816

Tx prefix hash: 358dc45a21bba9ed2a880841d88a25c63fb9384e429991e4ec87aaf3e316425b
Tx public key: 5690985ce5d4ac3deb69a4af0f459aeadf10d60b165b2f43bf7de5bc250b8d9a
Timestamp: 1694445716 Timestamp [UCT]: 2023-09-11 15:21:56 Age [y:d:h:m:s]: 01:206:06:10:04
Block: 845882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408505 RingCT/type: yes/0
Extra: 015690985ce5d4ac3deb69a4af0f459aeadf10d60b165b2f43bf7de5bc250b8d9a0211000000018bcdc0ce000000000000000000

1 output(s) for total of 0.966589013000 dcy

stealth address amount amount idx
00: 1134303e3728277dfab11d90d0d8f0c95f1a5d76d2dc2f652a40581ebbc121b1 0.966589013000 1299308 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": 845892, "vin": [ { "gen": { "height": 845882 } } ], "vout": [ { "amount": 966589013, "target": { "key": "1134303e3728277dfab11d90d0d8f0c95f1a5d76d2dc2f652a40581ebbc121b1" } } ], "extra": [ 1, 86, 144, 152, 92, 229, 212, 172, 61, 235, 105, 164, 175, 15, 69, 154, 234, 223, 16, 214, 11, 22, 91, 47, 67, 191, 125, 229, 188, 37, 11, 141, 154, 2, 17, 0, 0, 0, 1, 139, 205, 192, 206, 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