Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc70debacd6a8debc454d2f6ea5334eb2f65644694693c16998558ea2d11d5c3

Tx prefix hash: 8933a72ccbca8378db5ab08aaff43265dc0e3fd8f9b60af7492531229f4e5343
Tx public key: 248cb13338bf0178361f4e97112fb9440f8b025854e024203cd9a2a4ec6cb116
Timestamp: 1706897942 Timestamp [UCT]: 2024-02-02 18:19:02 Age [y:d:h:m:s]: 01:277:11:36:37
Block: 948919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457093 RingCT/type: yes/0
Extra: 01248cb13338bf0178361f4e97112fb9440f8b025854e024203cd9a2a4ec6cb116021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f937a20dbe8745a8681a2b7b5129c88271c2c658a0f9a0c5042d083bb7e70d 0.600000000000 1407433 of 15

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": 948929, "vin": [ { "gen": { "height": 948919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f937a20dbe8745a8681a2b7b5129c88271c2c658a0f9a0c5042d083bb7e70d" } } ], "extra": [ 1, 36, 140, 177, 51, 56, 191, 1, 120, 54, 31, 78, 151, 17, 47, 185, 68, 15, 139, 2, 88, 84, 224, 36, 32, 60, 217, 162, 164, 236, 108, 177, 22, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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