Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a116fafaac7cfaa88aa146b30890ab8f4f1e43fea7e246ee105ad6e313fc073

Tx prefix hash: e8e065aa6634f05de0dfbf53d5cafa8d4c0bf45fc70aeaac67dfdd87dec77b4d
Tx public key: 893f4d32612cec0b4506a52386467ce6ebb5057572daef449a25928fd37f475a
Timestamp: 1711376951 Timestamp [UCT]: 2024-03-25 14:29:11 Age [y:d:h:m:s]: 01:079:19:53:16
Block: 986089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317993 RingCT/type: yes/0
Extra: 01893f4d32612cec0b4506a52386467ce6ebb5057572daef449a25928fd37f475a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5c83e910aad406ebd38a30bf5bd4a749249e40a05e1d5a91e2d39fbf28f6195 0.600000000000 1446314 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": 986099, "vin": [ { "gen": { "height": 986089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5c83e910aad406ebd38a30bf5bd4a749249e40a05e1d5a91e2d39fbf28f6195" } } ], "extra": [ 1, 137, 63, 77, 50, 97, 44, 236, 11, 69, 6, 165, 35, 134, 70, 124, 230, 235, 181, 5, 117, 114, 218, 239, 68, 154, 37, 146, 143, 211, 127, 71, 90, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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