Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95865a105b830923559f82827cf9ffae580472c99291d3de256b40f0869294d

Tx prefix hash: b85e45d4afd581ba9f43b4cdd7561d3cadeef9178f4f78386666f418bc77a4b5
Tx public key: 7b8ca85b1392de9f0f874125c54c96b54bf2a14f2e3f00f5c60f820cafa1bd10
Timestamp: 1747142189 Timestamp [UCT]: 2025-05-13 13:16:29 Age [y:d:h:m:s]: 00:192:08:00:45
Block: 1282039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135175 RingCT/type: yes/0
Extra: 017b8ca85b1392de9f0f874125c54c96b54bf2a14f2e3f00f5c60f820cafa1bd100211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2877fdc69cda7fec82036889c81025891e076d4263f12fee11ec9c6a694fc8f0 0.600000000000 1769446 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": 1282049, "vin": [ { "gen": { "height": 1282039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2877fdc69cda7fec82036889c81025891e076d4263f12fee11ec9c6a694fc8f0" } } ], "extra": [ 1, 123, 140, 168, 91, 19, 146, 222, 159, 15, 135, 65, 37, 197, 76, 150, 181, 75, 242, 161, 79, 46, 63, 0, 245, 198, 15, 130, 12, 175, 161, 189, 16, 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