Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7459d5dc41f39de1c69f5d0824fdd37daa60b0d6090eded3e82445991e53d1ef

Tx prefix hash: e75caaaf6e97557a269dbaf0099a265fd3af2ef8f03d87f9028d0c03240e53d4
Tx public key: 7281561ff517e6c77c0b1d234d10703b7624d5fac9cef0e7e5334cb4db86e464
Timestamp: 1765969689 Timestamp [UCT]: 2025-12-17 11:08:09 Age [y:d:h:m:s]: 00:005:04:20:15
Block: 1435529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3708 RingCT/type: yes/0
Extra: 017281561ff517e6c77c0b1d234d10703b7624d5fac9cef0e7e5334cb4db86e4640211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd5f6764bb1e069b3ac9246e6ef324c2191a15905aff2139f20eb2d027752bc6 0.600000000000 1924326 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": 1435539, "vin": [ { "gen": { "height": 1435529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd5f6764bb1e069b3ac9246e6ef324c2191a15905aff2139f20eb2d027752bc6" } } ], "extra": [ 1, 114, 129, 86, 31, 245, 23, 230, 199, 124, 11, 29, 35, 77, 16, 112, 59, 118, 36, 213, 250, 201, 206, 240, 231, 229, 51, 76, 180, 219, 134, 228, 100, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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