Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4010cc440b00f67952fe619c820bcbdc9eb1dbeb1e39d0859d2a6c8968e07ad8

Tx prefix hash: 96782f0d883002393f961046c15e0cec975a9295489793b5fc260e4785ce1415
Tx public key: 5e9e89bb4fd6ef8be741aac7e05d0f39fb81fe9de39d85c3d35fbdd3703cc7ba
Timestamp: 1705082631 Timestamp [UCT]: 2024-01-12 18:03:51 Age [y:d:h:m:s]: 00:364:02:45:21
Block: 933864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260695 RingCT/type: yes/0
Extra: 015e9e89bb4fd6ef8be741aac7e05d0f39fb81fe9de39d85c3d35fbdd3703cc7ba02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20a1f6ca8446e7121302045a8912b25768a88195dbd54a311298231cad421f6d 0.600000000000 1391848 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": 933874, "vin": [ { "gen": { "height": 933864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20a1f6ca8446e7121302045a8912b25768a88195dbd54a311298231cad421f6d" } } ], "extra": [ 1, 94, 158, 137, 187, 79, 214, 239, 139, 231, 65, 170, 199, 224, 93, 15, 57, 251, 129, 254, 157, 227, 157, 133, 195, 211, 95, 189, 211, 112, 60, 199, 186, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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