Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 007ca44069340f28e5677f8539085b0d9bde83be7b8b6903b2c4c38f5a328549

Tx prefix hash: 3c7e3a50c8086c4971ee6483a2ef0ba8004751d7584af26bbb365d443c16b43e
Tx public key: 28d06ef2a7f69d36fbd3e7bcc7fb9d689217d9452f4c112048bd65b229370b61
Timestamp: 1714740702 Timestamp [UCT]: 2024-05-03 12:51:42 Age [y:d:h:m:s]: 00:337:14:19:56
Block: 1013959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241312 RingCT/type: yes/0
Extra: 0128d06ef2a7f69d36fbd3e7bcc7fb9d689217d9452f4c112048bd65b229370b610211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23dea31dded9c810a5c461615b2cda437ff8ec9959c9ca1bfa845b2da75f1ff1 0.600000000000 1476918 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": 1013969, "vin": [ { "gen": { "height": 1013959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23dea31dded9c810a5c461615b2cda437ff8ec9959c9ca1bfa845b2da75f1ff1" } } ], "extra": [ 1, 40, 208, 110, 242, 167, 246, 157, 54, 251, 211, 231, 188, 199, 251, 157, 104, 146, 23, 217, 69, 47, 76, 17, 32, 72, 189, 101, 178, 41, 55, 11, 97, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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