Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5cd36163d7835df1b92f2805d63469da848ac3fbe024eb86c0d589af8ac4a0

Tx prefix hash: d1ffaa099c24ae8ef1bd0a6805d0a60b8ece46479bd53b253ac766e00b6235cd
Tx public key: b8b93ac3c90c1ad079ce1bcbbf9a3492ab9a1a95885d9484cb6172fece4afb7d
Timestamp: 1724620919 Timestamp [UCT]: 2024-08-25 21:21:59 Age [y:d:h:m:s]: 00:274:21:36:39
Block: 1095859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196371 RingCT/type: yes/0
Extra: 01b8b93ac3c90c1ad079ce1bcbbf9a3492ab9a1a95885d9484cb6172fece4afb7d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ca4ff3d7b59a5ca5ed6509bbd694c863ec987bcc98f3a29f21904085a20567 0.600000000000 1571042 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": 1095869, "vin": [ { "gen": { "height": 1095859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ca4ff3d7b59a5ca5ed6509bbd694c863ec987bcc98f3a29f21904085a20567" } } ], "extra": [ 1, 184, 185, 58, 195, 201, 12, 26, 208, 121, 206, 27, 203, 191, 154, 52, 146, 171, 154, 26, 149, 136, 93, 148, 132, 203, 97, 114, 254, 206, 74, 251, 125, 2, 17, 0, 0, 0, 4, 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