Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0dd9f38d489b67974f8eea961113e8eac335f29ec106f36532bb4db790938b

Tx prefix hash: 111348ca3ce93da1cbc8c0133332ae7088401d55ed869321def92d847a9759f1
Tx public key: ed7de5b6c58423743f0091d2286c9c76e6eef3efc33942f3f5b25ecd4944a7f8
Timestamp: 1704913348 Timestamp [UCT]: 2024-01-10 19:02:28 Age [y:d:h:m:s]: 01:084:04:19:37
Block: 932467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321263 RingCT/type: yes/0
Extra: 01ed7de5b6c58423743f0091d2286c9c76e6eef3efc33942f3f5b25ecd4944a7f802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82939ab0e230a69c80aac3bfba14c79503a8e91ef188d2e6f3f4647c559ae98d 0.600000000000 1390403 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": 932477, "vin": [ { "gen": { "height": 932467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82939ab0e230a69c80aac3bfba14c79503a8e91ef188d2e6f3f4647c559ae98d" } } ], "extra": [ 1, 237, 125, 229, 182, 197, 132, 35, 116, 63, 0, 145, 210, 40, 108, 156, 118, 230, 238, 243, 239, 195, 57, 66, 243, 245, 178, 94, 205, 73, 68, 167, 248, 2, 17, 0, 0, 0, 2, 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