Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed35cdf0212f1ed32cec225794d90284eb6b879e11ad610cd20166d99c743a0

Tx prefix hash: 2efc919a1925c257cc68b8f945666c20bde18acac155a357a151494181294c96
Tx public key: 8a41e5e53cb3dcb910b97016d9e5996773df857f977af2691ecd500d8248afe3
Timestamp: 1576928021 Timestamp [UCT]: 2019-12-21 11:33:41 Age [y:d:h:m:s]: 05:314:20:48:29
Block: 29203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371891 RingCT/type: yes/0
Extra: 018a41e5e53cb3dcb910b97016d9e5996773df857f977af2691ecd500d8248afe3021100000049ad433a0b000000000000000000

1 output(s) for total of 491.178333993000 dcy

stealth address amount amount idx
00: b31d4cb1b286a39ebc68faf4a0fc3034b2fe0b933226f1dad28678b0e82784eb 491.178333993000 48031 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": 29213, "vin": [ { "gen": { "height": 29203 } } ], "vout": [ { "amount": 491178333993, "target": { "key": "b31d4cb1b286a39ebc68faf4a0fc3034b2fe0b933226f1dad28678b0e82784eb" } } ], "extra": [ 1, 138, 65, 229, 229, 60, 179, 220, 185, 16, 185, 112, 22, 217, 229, 153, 103, 115, 223, 133, 127, 151, 122, 242, 105, 30, 205, 80, 13, 130, 72, 175, 227, 2, 17, 0, 0, 0, 73, 173, 67, 58, 11, 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