Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56532e4a0a6c96c9838d155496014440ecb76f69fb7b939727221b279b1e14d

Tx prefix hash: 3b287e1e6eb62a82f374db49bf07ac446e694e671c09831eb95a8a45575e87b8
Tx public key: 3d98de42292cb6247338a4c5bae83ed76609713d935bdb14709cbf69bb96720d
Timestamp: 1695636068 Timestamp [UCT]: 2023-09-25 10:01:08 Age [y:d:h:m:s]: 01:264:04:24:31
Block: 855760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449834 RingCT/type: yes/0
Extra: 013d98de42292cb6247338a4c5bae83ed76609713d935bdb14709cbf69bb96720d02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.896420800000 dcy

stealth address amount amount idx
00: feba6716161c7b7a8636db52e8521a70e3642c44ee44d2f4ba8e51be763c4f55 0.896420800000 1309798 of 0

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": 855770, "vin": [ { "gen": { "height": 855760 } } ], "vout": [ { "amount": 896420800, "target": { "key": "feba6716161c7b7a8636db52e8521a70e3642c44ee44d2f4ba8e51be763c4f55" } } ], "extra": [ 1, 61, 152, 222, 66, 41, 44, 182, 36, 115, 56, 164, 197, 186, 232, 62, 215, 102, 9, 113, 61, 147, 91, 219, 20, 112, 156, 191, 105, 187, 150, 114, 13, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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