Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9daa90f246b18d6a1e7a3ab464ed029d8115d387bea3b35531daa4431a0de855

Tx prefix hash: a013e84ee8e6290e2462ff5cc17b48b9fad9fd917758263982d70505677201be
Tx public key: 536b9cf51b4acd0abe4da37bc87fb2b69596a4458ecf8ce5cd3326c946e7e299
Timestamp: 1707582378 Timestamp [UCT]: 2024-02-10 16:26:18 Age [y:d:h:m:s]: 00:250:22:02:16
Block: 954599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179743 RingCT/type: yes/0
Extra: 01536b9cf51b4acd0abe4da37bc87fb2b69596a4458ecf8ce5cd3326c946e7e29902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c0d140c3a8a33d1093cf1543d85426e952425b9490cb3e73a60083d9c9cc238 0.600000000000 1413879 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": 954609, "vin": [ { "gen": { "height": 954599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c0d140c3a8a33d1093cf1543d85426e952425b9490cb3e73a60083d9c9cc238" } } ], "extra": [ 1, 83, 107, 156, 245, 27, 74, 205, 10, 190, 77, 163, 123, 200, 127, 178, 182, 149, 150, 164, 69, 142, 207, 140, 229, 205, 51, 38, 201, 70, 231, 226, 153, 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