Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d9ea49baf073ac609b7466ffc2616d80b0234fa6d787ca3d96d43f6141a1d5e

Tx prefix hash: b75e80c75243c3e4f2772e5b8d882c5d9ac3eaddd9cee94dd6d3e5301296424b
Tx public key: 1367f2dce6a803db034d60eb0d7d3fe4449d8601eaecd39a3bd3efd8120671b3
Timestamp: 1736794186 Timestamp [UCT]: 2025-01-13 18:49:46 Age [y:d:h:m:s]: 00:155:05:49:17
Block: 1196643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110658 RingCT/type: yes/0
Extra: 011367f2dce6a803db034d60eb0d7d3fe4449d8601eaecd39a3bd3efd8120671b30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e9145a9eb30310ad8ac1cdf5c429ad41c9d52e28594c66d22005ea0a71cb89b 0.600000000000 1683244 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": 1196653, "vin": [ { "gen": { "height": 1196643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e9145a9eb30310ad8ac1cdf5c429ad41c9d52e28594c66d22005ea0a71cb89b" } } ], "extra": [ 1, 19, 103, 242, 220, 230, 168, 3, 219, 3, 77, 96, 235, 13, 125, 63, 228, 68, 157, 134, 1, 234, 236, 211, 154, 59, 211, 239, 216, 18, 6, 113, 179, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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