Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cace4162bb331c333de16bc13689feb92e19d7abb525003c8f553413e1012cb

Tx prefix hash: 37d6efa56aec59b146716153da93f938903a772cad40722b32a6951babecc4da
Tx public key: 8d6f2451951b1471c9b49373df1a1b3ce48c38574cc2c68faf5da9d53f7f6ec9
Timestamp: 1724720923 Timestamp [UCT]: 2024-08-27 01:08:43 Age [y:d:h:m:s]: 01:072:20:06:14
Block: 1096685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310508 RingCT/type: yes/0
Extra: 018d6f2451951b1471c9b49373df1a1b3ce48c38574cc2c68faf5da9d53f7f6ec9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c77f9d15429a129f370a890922226fbd77e4fb329cbec87c403b1ee5b99ceac 0.600000000000 1571878 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": 1096695, "vin": [ { "gen": { "height": 1096685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c77f9d15429a129f370a890922226fbd77e4fb329cbec87c403b1ee5b99ceac" } } ], "extra": [ 1, 141, 111, 36, 81, 149, 27, 20, 113, 201, 180, 147, 115, 223, 26, 27, 60, 228, 140, 56, 87, 76, 194, 198, 143, 175, 93, 169, 213, 63, 127, 110, 201, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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