Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13104bd18c6aed148f19f317787b1b36a4e351617260eb48fe5a842316ecc12a

Tx prefix hash: 9f029c21b1f6341bd40f5781f21f447cbf2c4b4f73ed53837725448460fc3323
Tx public key: abfc8a7a0fb079f33214d06ff669912d45e5df13b22472b6de58d3a874ef8442
Timestamp: 1730759606 Timestamp [UCT]: 2024-11-04 22:33:26 Age [y:d:h:m:s]: 00:146:12:50:24
Block: 1146669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104562 RingCT/type: yes/0
Extra: 01abfc8a7a0fb079f33214d06ff669912d45e5df13b22472b6de58d3a874ef8442021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f992fc9cbcbd3de8ceb524797f033968f2817c0b9fa0295913ea14cc9cb0bb1f 0.600000000000 1631360 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": 1146679, "vin": [ { "gen": { "height": 1146669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f992fc9cbcbd3de8ceb524797f033968f2817c0b9fa0295913ea14cc9cb0bb1f" } } ], "extra": [ 1, 171, 252, 138, 122, 15, 176, 121, 243, 50, 20, 208, 111, 246, 105, 145, 45, 69, 229, 223, 19, 178, 36, 114, 182, 222, 88, 211, 168, 116, 239, 132, 66, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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