Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede394d37a32e2a0ba7494c737954b633861b5a3a75f8ad6e42abde92705d40d

Tx prefix hash: 43d5e889dcaed7f7f3c4ceda3b1240f5af032ab80d3b52fc5ec3945faa9f8e68
Tx public key: ae36fa0a97c19d2b55536b4e3bb7dd0849d69aa790b6f6e7d5cd944bb9cee6f4
Timestamp: 1714009569 Timestamp [UCT]: 2024-04-25 01:46:09 Age [y:d:h:m:s]: 01:009:14:16:33
Block: 1007881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267809 RingCT/type: yes/0
Extra: 01ae36fa0a97c19d2b55536b4e3bb7dd0849d69aa790b6f6e7d5cd944bb9cee6f40211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 571c2068be786f760e3e18677f609416ee1cb2f7b137642ef21892ae8013fa8a 0.600000000000 1469347 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": 1007891, "vin": [ { "gen": { "height": 1007881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "571c2068be786f760e3e18677f609416ee1cb2f7b137642ef21892ae8013fa8a" } } ], "extra": [ 1, 174, 54, 250, 10, 151, 193, 157, 43, 85, 83, 107, 78, 59, 183, 221, 8, 73, 214, 154, 167, 144, 182, 246, 231, 213, 205, 148, 75, 185, 206, 230, 244, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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