Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0af158099c719268b99a34ae44e8c03c9b67d138f13eae5251bd683b0fa7148

Tx prefix hash: 1e5d17d7354d4913a47283ce6593f7d6c30ca06472970c5185ea78a2090897ac
Tx public key: f32d513fb85249c8d69a4085011e0fca31ab21d1015ef529b487ca2862e521ba
Timestamp: 1726717811 Timestamp [UCT]: 2024-09-19 03:50:11 Age [y:d:h:m:s]: 00:115:07:11:24
Block: 1113245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82451 RingCT/type: yes/0
Extra: 01f32d513fb85249c8d69a4085011e0fca31ab21d1015ef529b487ca2862e521ba02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9351681fc1a7a43f074522c32ba3cbbe5a21e54f8d5ac504ca4a4bb5e28b559f 0.600000000000 1592850 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": 1113255, "vin": [ { "gen": { "height": 1113245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9351681fc1a7a43f074522c32ba3cbbe5a21e54f8d5ac504ca4a4bb5e28b559f" } } ], "extra": [ 1, 243, 45, 81, 63, 184, 82, 73, 200, 214, 154, 64, 133, 1, 30, 15, 202, 49, 171, 33, 209, 1, 94, 245, 41, 180, 135, 202, 40, 98, 229, 33, 186, 2, 17, 0, 0, 0, 5, 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