Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46755d415ba88aa8cf3e1b476cdeb8f4571e6831b991c08570428f8d6045241c

Tx prefix hash: 2f03696ca46f0b4e87ea66770927eb880b3e374ce8f7b1fb515ae977b6cfcc5f
Tx public key: 12f69bcfa02958d103e9ff85b277b52f9a45c6d7430f1b8818edee9f4103a114
Timestamp: 1746229865 Timestamp [UCT]: 2025-05-02 23:51:05 Age [y:d:h:m:s]: 00:202:16:03:45
Block: 1274493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142549 RingCT/type: yes/0
Extra: 0112f69bcfa02958d103e9ff85b277b52f9a45c6d7430f1b8818edee9f4103a1140211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a94d67235fed8fa8bdc3b2180ea63644e9bee05faba2cb38de9c63e8375e246a 0.600000000000 1761788 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": 1274503, "vin": [ { "gen": { "height": 1274493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a94d67235fed8fa8bdc3b2180ea63644e9bee05faba2cb38de9c63e8375e246a" } } ], "extra": [ 1, 18, 246, 155, 207, 160, 41, 88, 209, 3, 233, 255, 133, 178, 119, 181, 47, 154, 69, 198, 215, 67, 15, 27, 136, 24, 237, 238, 159, 65, 3, 161, 20, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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