Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f396239b754c59d448e7e0a5becb6caf3bf9364d6e4ca76aa93bda59221b9c53

Tx prefix hash: 095db4000ff68553c4ab131708b039aa788b2f962a60230c1d37239e35b9ce13
Tx public key: dd711d75c178c663d24147a480d079d7d44b6634924edc9c1b5f493aef57558e
Timestamp: 1719153149 Timestamp [UCT]: 2024-06-23 14:32:29 Age [y:d:h:m:s]: 01:196:09:12:51
Block: 1050519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399015 RingCT/type: yes/0
Extra: 01dd711d75c178c663d24147a480d079d7d44b6634924edc9c1b5f493aef57558e02110000000d0fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d3aad0abc4109dce25ae347ee05e1f5462ecd3d20edeef991770e93ada3cbdf 0.600000000000 1520694 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": 1050529, "vin": [ { "gen": { "height": 1050519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d3aad0abc4109dce25ae347ee05e1f5462ecd3d20edeef991770e93ada3cbdf" } } ], "extra": [ 1, 221, 113, 29, 117, 193, 120, 198, 99, 210, 65, 71, 164, 128, 208, 121, 215, 212, 75, 102, 52, 146, 78, 220, 156, 27, 95, 73, 58, 239, 87, 85, 142, 2, 17, 0, 0, 0, 13, 15, 187, 196, 197, 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