Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c89f413073589146040960145f366a4d419d02e6d11ffb0ed80e347ed75daca6

Tx prefix hash: 92913159ad2fb6f3b7c05446955a41840addaa6f0d5cb486d06d5351180a9e2d
Tx public key: edb1a688be8ea270d20f8b990e7f7350176ee56bb2b39bd807296a18490a35b5
Timestamp: 1725753249 Timestamp [UCT]: 2024-09-07 23:54:09 Age [y:d:h:m:s]: 00:264:21:39:57
Block: 1105252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189216 RingCT/type: yes/0
Extra: 01edb1a688be8ea270d20f8b990e7f7350176ee56bb2b39bd807296a18490a35b5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14c6ff4d8a929e31f496523e2d33ae0d5c269e230a083dc86ea335e729fdc4fc 0.600000000000 1582593 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": 1105262, "vin": [ { "gen": { "height": 1105252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14c6ff4d8a929e31f496523e2d33ae0d5c269e230a083dc86ea335e729fdc4fc" } } ], "extra": [ 1, 237, 177, 166, 136, 190, 142, 162, 112, 210, 15, 139, 153, 14, 127, 115, 80, 23, 110, 229, 107, 178, 179, 155, 216, 7, 41, 106, 24, 73, 10, 53, 181, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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