Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5e87b6d694eedea13f14c571c418e4c5bc65371c998d49f88ab69f700918b0f

Tx prefix hash: d68bb7a198a3ba91fe01b2494768058ad72fd499d3730e5cfe9bdc5d5669bbb3
Tx public key: 30883f5a974ecf67e8b32c752efb73e16a4d0a02b60d6f805fc1c5e8c8f4cacf
Timestamp: 1584511817 Timestamp [UCT]: 2020-03-18 06:10:17 Age [y:d:h:m:s]: 04:286:10:37:27
Block: 84770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100366 RingCT/type: yes/0
Extra: 0130883f5a974ecf67e8b32c752efb73e16a4d0a02b60d6f805fc1c5e8c8f4cacf0211000000248a2ee0d9000000000000000000

1 output(s) for total of 321.456774929000 dcy

stealth address amount amount idx
00: 02566712e73ae4749ab74624b7a61524c537642ecb9dca50e8844209cc2ead1e 321.456774929000 153486 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": 84780, "vin": [ { "gen": { "height": 84770 } } ], "vout": [ { "amount": 321456774929, "target": { "key": "02566712e73ae4749ab74624b7a61524c537642ecb9dca50e8844209cc2ead1e" } } ], "extra": [ 1, 48, 136, 63, 90, 151, 78, 207, 103, 232, 179, 44, 117, 46, 251, 115, 225, 106, 77, 10, 2, 182, 13, 111, 128, 95, 193, 197, 232, 200, 244, 202, 207, 2, 17, 0, 0, 0, 36, 138, 46, 224, 217, 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