Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3e8041481b7f2c75bb2bd1c2775a73987dff5ca77f1e0b7a3926c400636b66d

Tx prefix hash: 891353ebbde3521be6843902b9c2033a088a6e0459a264dd1499d29281f0d8f7
Tx public key: 67e98e1ce447e6822b0ea08cbc443d944ea89fcfe3aecd23d8fc7f01618086ba
Timestamp: 1580888216 Timestamp [UCT]: 2020-02-05 07:36:56 Age [y:d:h:m:s]: 05:029:07:16:19
Block: 59003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173023 RingCT/type: yes/0
Extra: 0167e98e1ce447e6822b0ea08cbc443d944ea89fcfe3aecd23d8fc7f01618086ba0211000000012264afe6000000000000000000

1 output(s) for total of 391.290575259000 dcy

stealth address amount amount idx
00: 43187a7b5875786ac651abacb9a5438734964f10d0cf8a578faa6a90420ea9af 391.290575259000 108983 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": 59013, "vin": [ { "gen": { "height": 59003 } } ], "vout": [ { "amount": 391290575259, "target": { "key": "43187a7b5875786ac651abacb9a5438734964f10d0cf8a578faa6a90420ea9af" } } ], "extra": [ 1, 103, 233, 142, 28, 228, 71, 230, 130, 43, 14, 160, 140, 188, 68, 61, 148, 78, 168, 159, 207, 227, 174, 205, 35, 216, 252, 127, 1, 97, 128, 134, 186, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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