Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273351706fc5d47aeb90ee43798f10f966e0d1e78186bc114b42d3b87dbcb9f9

Tx prefix hash: 3796ca32b7ca41d91916714e632106e723336f7a1c73ca4f67721864b36b7558
Tx public key: d3f5ad91ce3fe4ba7e5b3cac05473a30c8547b2042c1e59fd1ec4f107f460302
Timestamp: 1714915054 Timestamp [UCT]: 2024-05-05 13:17:34 Age [y:d:h:m:s]: 00:293:20:06:41
Block: 1015406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209998 RingCT/type: yes/0
Extra: 01d3f5ad91ce3fe4ba7e5b3cac05473a30c8547b2042c1e59fd1ec4f107f46030202110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44a3512b03bbf945bad30cc7ad970c3d0686c69909fe665b9f70d6c9d54106f 0.600000000000 1478759 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": 1015416, "vin": [ { "gen": { "height": 1015406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44a3512b03bbf945bad30cc7ad970c3d0686c69909fe665b9f70d6c9d54106f" } } ], "extra": [ 1, 211, 245, 173, 145, 206, 63, 228, 186, 126, 91, 60, 172, 5, 71, 58, 48, 200, 84, 123, 32, 66, 193, 229, 159, 209, 236, 79, 16, 127, 70, 3, 2, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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