Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd44ef1d7c275e227c72d27511fb159f5ca9ef9bcb2e2fa94b693df16eee19fd

Tx prefix hash: 1332f8cc26862bc626c61ab0aec328a65f9fdfb6ffbd7243d0d36e50a5b5957e
Tx public key: 28d3b97a4393ed41b4c6cc9acbc9737ed5caa8563ff5fa6d32ec2dcee5491309
Timestamp: 1577701048 Timestamp [UCT]: 2019-12-30 10:17:28 Age [y:d:h:m:s]: 05:000:13:29:09
Block: 34932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150414 RingCT/type: yes/0
Extra: 0128d3b97a4393ed41b4c6cc9acbc9737ed5caa8563ff5fa6d32ec2dcee54913090211000000044ac5aa02000000000000000000

1 output(s) for total of 470.171865686000 dcy

stealth address amount amount idx
00: e0f6ce1d5476de2aeb00fb35b6c92b54a398a2e82e1710793cdb49e5e77c061c 470.171865686000 58849 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": 34942, "vin": [ { "gen": { "height": 34932 } } ], "vout": [ { "amount": 470171865686, "target": { "key": "e0f6ce1d5476de2aeb00fb35b6c92b54a398a2e82e1710793cdb49e5e77c061c" } } ], "extra": [ 1, 40, 211, 185, 122, 67, 147, 237, 65, 180, 198, 204, 154, 203, 201, 115, 126, 213, 202, 168, 86, 63, 245, 250, 109, 50, 236, 45, 206, 229, 73, 19, 9, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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