Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e54334511a1c5bb6ff81076fbdbc97bc4466cfc75adeed5fab3f76b921dc8cf0

Tx prefix hash: e2af3c6630621d93a770cea2f6468511a76e2c6d0bc4d8b729c8569c9af5cb28
Tx public key: a0bc9b91d451dda5e798365186683aac31c96ceb82f6f8a42336fdd6a84c385d
Timestamp: 1708142743 Timestamp [UCT]: 2024-02-17 04:05:43 Age [y:d:h:m:s]: 01:040:18:21:30
Block: 959247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290166 RingCT/type: yes/0
Extra: 01a0bc9b91d451dda5e798365186683aac31c96ceb82f6f8a42336fdd6a84c385d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f6387260ecf795416437906fa514ab1f5eab23ca43cf0a3fcf7ee7dc7b927c 0.600000000000 1418778 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": 959257, "vin": [ { "gen": { "height": 959247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f6387260ecf795416437906fa514ab1f5eab23ca43cf0a3fcf7ee7dc7b927c" } } ], "extra": [ 1, 160, 188, 155, 145, 212, 81, 221, 165, 231, 152, 54, 81, 134, 104, 58, 172, 49, 201, 108, 235, 130, 246, 248, 164, 35, 54, 253, 214, 168, 76, 56, 93, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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