Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1feacd4e2e8736d70f27a366b41291908eb2d4e4c5824f2c0ddba2a06732f59c

Tx prefix hash: d34b8ea8a3fd5e16bf1beeddb265efdf94ce423afdbb89824c6bbd8663679700
Tx public key: 60c65c78b9990bfc28eb280a0dbf56ca40c8eca8c1e9302cf51ef4077fa29d60
Timestamp: 1738126624 Timestamp [UCT]: 2025-01-29 04:57:04 Age [y:d:h:m:s]: 00:321:06:54:06
Block: 1207423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227415 RingCT/type: yes/0
Extra: 0160c65c78b9990bfc28eb280a0dbf56ca40c8eca8c1e9302cf51ef4077fa29d600211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb4c6861494e0a3a5d2e239b01d01d9ec80af95d2182b4265ad83de9cd38e4cc 0.600000000000 1694146 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": 1207433, "vin": [ { "gen": { "height": 1207423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb4c6861494e0a3a5d2e239b01d01d9ec80af95d2182b4265ad83de9cd38e4cc" } } ], "extra": [ 1, 96, 198, 92, 120, 185, 153, 11, 252, 40, 235, 40, 10, 13, 191, 86, 202, 64, 200, 236, 168, 193, 233, 48, 44, 245, 30, 244, 7, 127, 162, 157, 96, 2, 17, 0, 0, 0, 1, 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