Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed0fdd06b0d11053a8da8ad80bcd5ed8590e49b5449f8e708239a704772d089

Tx prefix hash: 74e77b681db1b86fa2e58dc65b23bd0a52cb2feed2c81301ce86da6fff552fbd
Tx public key: c18ec2ebe9735f95e41f2487e8f6a46cd20cc1652c9f06120c5a06f99d16a079
Timestamp: 1726568724 Timestamp [UCT]: 2024-09-17 10:25:24 Age [y:d:h:m:s]: 01:051:18:47:08
Block: 1112007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295427 RingCT/type: yes/0
Extra: 01c18ec2ebe9735f95e41f2487e8f6a46cd20cc1652c9f06120c5a06f99d16a07902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c47292519a6227b57f3ac1ba3bd1d97ce704234a20aa90619a83ab8aadc2358 0.600000000000 1591170 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": 1112017, "vin": [ { "gen": { "height": 1112007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c47292519a6227b57f3ac1ba3bd1d97ce704234a20aa90619a83ab8aadc2358" } } ], "extra": [ 1, 193, 142, 194, 235, 233, 115, 95, 149, 228, 31, 36, 135, 232, 246, 164, 108, 210, 12, 193, 101, 44, 159, 6, 18, 12, 90, 6, 249, 157, 22, 160, 121, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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