Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010996d12760ec50adc421232322cacb4169c8b2118c0d216fed8e604e80bd17

Tx prefix hash: 88b665d6da480b04ffc44e2e76bc90cfe42def1d627442da768ceb077530d81d
Tx public key: ad07831e2a3f0c829af4031826bd720a6044d41fec6ab1b2df7cdef24620725d
Timestamp: 1577228974 Timestamp [UCT]: 2019-12-24 23:09:34 Age [y:d:h:m:s]: 04:340:09:25:48
Block: 31061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132369 RingCT/type: yes/0
Extra: 01ad07831e2a3f0c829af4031826bd720a6044d41fec6ab1b2df7cdef24620725d0211000000074ac5aa02000000000000000000

1 output(s) for total of 484.264767980000 dcy

stealth address amount amount idx
00: 648c9e9c9be2c0a5eb66f4116927464c82d324ec544c08a8963f06f897c0013d 484.264767980000 51331 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": 31071, "vin": [ { "gen": { "height": 31061 } } ], "vout": [ { "amount": 484264767980, "target": { "key": "648c9e9c9be2c0a5eb66f4116927464c82d324ec544c08a8963f06f897c0013d" } } ], "extra": [ 1, 173, 7, 131, 30, 42, 63, 12, 130, 154, 244, 3, 24, 38, 189, 114, 10, 96, 68, 212, 31, 236, 106, 177, 178, 223, 124, 222, 242, 70, 32, 114, 93, 2, 17, 0, 0, 0, 7, 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