Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d54f49818370f6a949a1f6605810e49161dc798710e30d30daaa8726519eb8f

Tx prefix hash: aa7115600888473192d5f6704e29cc0a13385c924409de32fb049cb03e826f7b
Tx public key: 90fd1b859f74d1083b2ac75e6253af326b5334517d3ecbb2c0d39c0036b3722e
Timestamp: 1730073657 Timestamp [UCT]: 2024-10-28 00:00:57 Age [y:d:h:m:s]: 01:072:20:04:54
Block: 1141007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310557 RingCT/type: yes/0
Extra: 0190fd1b859f74d1083b2ac75e6253af326b5334517d3ecbb2c0d39c0036b3722e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 051f5fe2a9eb60cb2b606bf7a62946c95d511a201a479915bfc3f93d03f2464f 0.600000000000 1624814 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": 1141017, "vin": [ { "gen": { "height": 1141007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "051f5fe2a9eb60cb2b606bf7a62946c95d511a201a479915bfc3f93d03f2464f" } } ], "extra": [ 1, 144, 253, 27, 133, 159, 116, 209, 8, 59, 42, 199, 94, 98, 83, 175, 50, 107, 83, 52, 81, 125, 62, 203, 178, 192, 211, 156, 0, 54, 179, 114, 46, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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