Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0cf108ad714bab0c333d35bf3d2a4050ae1940e98a8eecbf9f4a044a143c558

Tx prefix hash: b30f1de4c2198883139624a6d1b8a497fa162ddbd105371d41f44d6c743207c4
Tx public key: 3185e9cd92b05dfd3ac33bd88bb99fe276e1251d185e8718be2c4fa0e5d60cc5
Timestamp: 1703121694 Timestamp [UCT]: 2023-12-21 01:21:34 Age [y:d:h:m:s]: 01:144:17:07:44
Block: 917644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364565 RingCT/type: yes/0
Extra: 013185e9cd92b05dfd3ac33bd88bb99fe276e1251d185e8718be2c4fa0e5d60cc5021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68bdf14a1d2dfacc4213a40f44ba6f4343187840f0d4661ecaedb3e5f7b4804c 0.600000000000 1375226 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": 917654, "vin": [ { "gen": { "height": 917644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68bdf14a1d2dfacc4213a40f44ba6f4343187840f0d4661ecaedb3e5f7b4804c" } } ], "extra": [ 1, 49, 133, 233, 205, 146, 176, 93, 253, 58, 195, 59, 216, 139, 185, 159, 226, 118, 225, 37, 29, 24, 94, 135, 24, 190, 44, 79, 160, 229, 214, 12, 197, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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