Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d86b6cbfde26c42eff4811a0f7dea06a40a5c7455f2cd83fd801a3f1636b591a

Tx prefix hash: 80b0c5e1e447af0347548f3c02cc654ae289c13b3a7eb7ef4cdaa1a2ea7a5044
Tx public key: 140fe4936debbf90457e8ef0baad231501a6ef6233d1fc131574c7802eb403ca
Timestamp: 1714248867 Timestamp [UCT]: 2024-04-27 20:14:27 Age [y:d:h:m:s]: 01:018:07:10:57
Block: 1009870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274025 RingCT/type: yes/0
Extra: 01140fe4936debbf90457e8ef0baad231501a6ef6233d1fc131574c7802eb403ca02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87efec78aae1b0b40a0e6a71f9a4d931e263544d9a24daca87f338b36a6afe69 0.600000000000 1471662 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": 1009880, "vin": [ { "gen": { "height": 1009870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87efec78aae1b0b40a0e6a71f9a4d931e263544d9a24daca87f338b36a6afe69" } } ], "extra": [ 1, 20, 15, 228, 147, 109, 235, 191, 144, 69, 126, 142, 240, 186, 173, 35, 21, 1, 166, 239, 98, 51, 209, 252, 19, 21, 116, 199, 128, 46, 180, 3, 202, 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