Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 049f13a5b0301abc22725e04941b0396429eb3b128cc9d6dc15206c315654157

Tx prefix hash: b118a09a663e9ff744274516d1e22a44cd7a3ea3069af97e7996af73b232f432
Tx public key: e8222684856cad7178007f2c3b0326ecc54baa758e2faec03123903ce4f4e8b2
Timestamp: 1702515836 Timestamp [UCT]: 2023-12-14 01:03:56 Age [y:d:h:m:s]: 01:038:07:54:38
Block: 912604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288704 RingCT/type: yes/0
Extra: 01e8222684856cad7178007f2c3b0326ecc54baa758e2faec03123903ce4f4e8b2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f4df15c0f994de7ea55d1d568848add43a9ba282cd5eefb8da70681c0034e7f 0.600000000000 1369836 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": 912614, "vin": [ { "gen": { "height": 912604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f4df15c0f994de7ea55d1d568848add43a9ba282cd5eefb8da70681c0034e7f" } } ], "extra": [ 1, 232, 34, 38, 132, 133, 108, 173, 113, 120, 0, 127, 44, 59, 3, 38, 236, 197, 75, 170, 117, 142, 47, 174, 192, 49, 35, 144, 60, 228, 244, 232, 178, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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