Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594452ea92bf9323866a5d9e193ced8bba47e89775da99364aa913c35f3c4a8f

Tx prefix hash: 6619cf45c85c380fbe75f1de38fb6e79cafb35c9acc654ed613c14a72359c365
Tx public key: f8e64c772fb73597e614384f4bb94207a66829d3468f6895c025a1b2bb67c5ef
Timestamp: 1704091731 Timestamp [UCT]: 2024-01-01 06:48:51 Age [y:d:h:m:s]: 01:095:18:08:09
Block: 925663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329540 RingCT/type: yes/0
Extra: 01f8e64c772fb73597e614384f4bb94207a66829d3468f6895c025a1b2bb67c5ef0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34a6f0b00f1b26f5002934b124110ecda1854b4f09d0dff7831ff2d85e3a311e 0.600000000000 1383429 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": 925673, "vin": [ { "gen": { "height": 925663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34a6f0b00f1b26f5002934b124110ecda1854b4f09d0dff7831ff2d85e3a311e" } } ], "extra": [ 1, 248, 230, 76, 119, 47, 183, 53, 151, 230, 20, 56, 79, 75, 185, 66, 7, 166, 104, 41, 211, 70, 143, 104, 149, 192, 37, 161, 178, 187, 103, 197, 239, 2, 17, 0, 0, 0, 6, 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