Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 172e4ba4e3499acff11d0c9a14416a962efa24a073f6aa790208acc4a2c5a3f6

Tx prefix hash: c8518f47289e1f6dac0e32eca62a84f100417a48ac42b9232663b0d05ed00c1d
Tx public key: 4c40f0f894c446b00c28f4c3ff21e57b23b2562ab9f690bff022d96a7af8aad5
Timestamp: 1658903120 Timestamp [UCT]: 2022-07-27 06:25:20 Age [y:d:h:m:s]: 02:291:11:17:59
Block: 552642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 729544 RingCT/type: yes/0
Extra: 014c40f0f894c446b00c28f4c3ff21e57b23b2562ab9f690bff022d96a7af8aad5021100000002ea8cbb85000000000000000000

1 output(s) for total of 9.054568733000 dcy

stealth address amount amount idx
00: d81063ecb6ece91c3af951b19bb8021fc27c8b7b05e91b7e0092da01961c3926 9.054568733000 984370 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": 552652, "vin": [ { "gen": { "height": 552642 } } ], "vout": [ { "amount": 9054568733, "target": { "key": "d81063ecb6ece91c3af951b19bb8021fc27c8b7b05e91b7e0092da01961c3926" } } ], "extra": [ 1, 76, 64, 240, 248, 148, 196, 70, 176, 12, 40, 244, 195, 255, 33, 229, 123, 35, 178, 86, 42, 185, 246, 144, 191, 240, 34, 217, 106, 122, 248, 170, 213, 2, 17, 0, 0, 0, 2, 234, 140, 187, 133, 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