Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f6a4e92cb63d3518413b01a247104d882f4448e0fa15d02b9f341d6b6f23b0

Tx prefix hash: 0c1129edb75b8bc6125f6c0039f300394de0ff753ac22e43c6b6d4375c747b1d
Tx public key: c944b5fb062f2bb02639c8f002578333de966c855235200dbae17e7a07f227c5
Timestamp: 1720180013 Timestamp [UCT]: 2024-07-05 11:46:53 Age [y:d:h:m:s]: 00:279:19:33:33
Block: 1059040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199940 RingCT/type: yes/0
Extra: 01c944b5fb062f2bb02639c8f002578333de966c855235200dbae17e7a07f227c50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf81a5c62c0af318ee31e18403f5339d8a1158c6c11906cf430ae221cb842a6 0.600000000000 1529499 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": 1059050, "vin": [ { "gen": { "height": 1059040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf81a5c62c0af318ee31e18403f5339d8a1158c6c11906cf430ae221cb842a6" } } ], "extra": [ 1, 201, 68, 181, 251, 6, 47, 43, 176, 38, 57, 200, 240, 2, 87, 131, 51, 222, 150, 108, 133, 82, 53, 32, 13, 186, 225, 126, 122, 7, 242, 39, 197, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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