Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94452e9d877778aed366c7a9dd31b05b080a1a261e50fd6af79b42cb09c07985

Tx prefix hash: 542f809207e086b65444e30eda97b3f605db6b65fb2414da15d949a462a7cc53
Tx public key: 688d8610509b4dc111bc0d4b7be5b0661f36537cf22e7d7639b33a1e79493e0c
Timestamp: 1712356731 Timestamp [UCT]: 2024-04-05 22:38:51 Age [y:d:h:m:s]: 01:051:21:45:41
Block: 994155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298121 RingCT/type: yes/0
Extra: 01688d8610509b4dc111bc0d4b7be5b0661f36537cf22e7d7639b33a1e79493e0c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c311a5c272f5debdad053eb050a557703fb0534a67b289f20947a1f8ab0e069 0.600000000000 1454557 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": 994165, "vin": [ { "gen": { "height": 994155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c311a5c272f5debdad053eb050a557703fb0534a67b289f20947a1f8ab0e069" } } ], "extra": [ 1, 104, 141, 134, 16, 80, 155, 77, 193, 17, 188, 13, 75, 123, 229, 176, 102, 31, 54, 83, 124, 242, 46, 125, 118, 57, 179, 58, 30, 121, 73, 62, 12, 2, 17, 0, 0, 0, 5, 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